I meant that you can override the == operator (write your own definition) in any class you create and it will be called rather than the default Object behaviour.

Also, probably shouldn’t have said C++. I’m way too rusty on it and it looks like I’m a bit off with that suggestion (read: wrong). Java might have been more appropriate - or any language where everything is considered an object.

My intention was to suggest that in language similar to C#, the == operator will return false for two separate non-primitives regardless of their actual value.

That aside, use of the Equals function makes sense as long as you know what it means. You get the same behaviour with C++.

Unless you’ve overridden the behaviour for a class, Equals() gives you value equality and == gives you reference equality. For unboxed primitives, == will give the same answer as Equals.

Also, as a side note, you can actually override operators in C#: http://msdn.microsoft.com/en-us/library/ms173147(VS.80).aspx.