Forking this feature request from #16

Original post: #16 (comment) by @MrJul

Pertinent APIs: http://source.roslyn.codeplex.com/#Microsoft.CodeAnalysis.Workspaces/Shared/Utilities/SymbolEquivalenceComparer.cs,f93cc1c775e51f8b

I've personally seen different developers within my own team hit upon the snag of not being able to correctly compare ISymbols that originate from different Compilations, and each try to come up with their own solution for it. It would be much better if there was a 'one true way' to do this.