oh right, did we decide eventually that we didn't like multiple returns in the one method ?? :-)
Nah, that's just the way I like to do it.
To be honest, though I suppose the instanceof is neccessary for robustness sakes, I wouldn't normally include it for a comparable implemented class. You're very rarely in the situation where some collection is going to be filled with a bunch of objects that aren't extended from a particular sub object, or all implement a particular interface.
Yeah, the chance is minimal, but you should always program for robustness from the start. It is easier to than spotting a bug.