Rambling reply.
For your simple example, probably not but using the Index number of the worksheet or the Code Name from the VBA properties window would be (ever so slightly) more efficient.
Where the Object.Object. syntax slows down (processor speed wise) is when walking down the object tree
VBA can then reference the range directly instead of having to resolve the various objects down to the range.
Whether or not this makes a noticable difference to the speed of execution is doubtful but if the code is running in a loop then obviously the savings increase with each iteration.
But setting references like that does help coding - there's less physical typing and and can help to avoid typos if you misspell a variable name (You do use 'Option Explicit', of course?)
Bookmarks