Why should the most restrictive condition be listed last in the where clause?
That was the case many years ago (back when I started working with databases).  These days however the optimizers are smart enough that it doesn't matter what order you put the restrictions in the WHERE clause.

What @PieterGeerkens mentioned was something called caching where the optimizer is smart enough to take the information it needed for the query you ran and put it into memory.  This of course provides much quicker access than disk IO.  Then when you run the second query all (or most depending on the size of your data and RAM) of your data will already be in memory.  This means that your second query will go faster.  And again as Pieter said if you clear your cache then run the queries in reverse order the second query will again go faster.

I'm hoping your book is just really old but either way I would find a different one.  There are a number of good free books out there along with other free training materials.  Here is a page with some good links.  http://sqlstudies.com/study-and-reference-tools/