Hashtable.Item thread safety

Unless synchronized with Hashtable.Synchronized() no methods of Hashtable are thread-safe. If multiple threads are accessing the same Hashtable, synchronizing is never "unnecessary overhead".

I was looking at the disassembly produced by .NET Reflector for the Hashtable class and this is what I found:
The Hashtable.Synchronized method returns a SyncHashtable instance which is a wrapper around the original Hashtable, the getter for the Item property for this wrapper just plain calls the original Hashtable's getter without making any locks, as opposed to the setter which does make a lock on the Hashtable.
So I understand, from this, that reads on the Item property are thread safe, but also that it doesn't hurt, speaking in terms of performance, to use Hashtable.Synchronized, which is probably a good idea if it will be used in a multithreaded application, so you don't need to change that code if you later need that synchronization for whatever reason.
Is all this too obvious?