You might not use the alias but you should.
Whenever the view is referenced in the code wither in an @DBLookup or a getview method the alias should be used.
This means that if your user/customer wishes to change the title of a view then you can do this easily, without fear of breaking the database functionality.
If you decide a view must become hidden then this will not alter your code either as you can put the brackets around the viewname without affecting the alias.
Using aliases is even easier in R5 because the aliases are displayed in the design views list.
There are no Exceptions to this rule as far as I know.
If you find a database that has these problems, just fill them in as you go along, or spend a few hours creating the aliases.