VA does not seem to be able to tell the difference between overloaded methods. e.g. if you select 'Find References' for an overloaded method, VA will return the references to all overloaded versions of the method instead of just the one version that was selected.
Will this ever be fixed? I assume you current only store the method name instead of a 'mangled' version of the name that includes parameter information.
Differentiate between overloaded methods in find references is on our list to consider:
case=2732
But don't hold your breath: our parser don't understand overloaded methods currently, this is why alt-g does not know which overload to jump to, and offers you all of them.
I also noticed this problem when trying to rename a method - it renames all of them regardless of parameters. This is not very nice. Are there any plans to fix this in near future?
It is on our list of things to fix, but it is a hard problem. You have to allow for implicit casts, overloaded casting operators, etc, to try and work out which overload is actually being called.