Not sure if Tim wants that, but at least that is the exact way things are in VAST. Opening the hierarchy Browser on a class shows the whole tree up to Object and down the whole subtree. I use this very often and don't really see why you may think this is a bad idea? In existing code, it can be extremely important to understand all implementations of a method in the whole tree. I would guess that this is the second most used Browser in my workflow, right after the Debugger/Inspector duo.