References to fields inside anon structs contain an implicit children
for the container, which has the same SourceLocation with the field.
This was resulting in SelectionTree always picking the anon-struct rather than
the field as the selection.
This patch prevents that by claiming the range for the field early.
seems like it'd be more consistent to handle it here?
If it's a MemberExpr and the member is in an anonymous struct, then it's implicit if isImplicit(ME.getBase()).