OP here. Thanks for the responses so far.
My question was based on the idea of working with non-built-in types. The gotcha that triggered this question came from our in-house smart pointer class. If a function returns a smart pointer, the reference count is increased and the caller is responsible for releasing it.
So if you use an = sign instead of our .Attach() call when calling something which returns a smart pointer (and assuming you want to take ownership of the pointer that's returned), you'll get a memory leak. (The = sign is supposed to be used to reference an object and use it for later.)
The equals sign is normally an innocent-looking thing, so I was looking for a way to highlight them when using this class to indicate that they're not "normal".
Another thought -- is there any way to highlight an operator and do a F12 (or something similar) to quickly jump to the overloaded operator code?