I am seeing the same problem, but not with this sample code. The problem happens in the solution, but the trigger involves a duplicate class and member function name as well as the using line:
case=34692
It is possible to confuse our parser with duplicate names, and here the using places the two classes into the same scope.