VEMap.FindLocation Suggests Addresses That Don't Geocode

Example... do a search using:

map.FindLocation('Chicago, IL', FindLocationCallback);

The FindLocationCallback function receives an array of two VESearchResult objects that contain the addresses of 'Chicago, Illinois, United States' and 'Chicago (river), Illinois, United States'

If you use either of these values and call the function again:

map.FindLocation('Chicago, Illinois, United States', FindLocationCallback);

the FindLocationCallback receives the same array of two VESearchResult objects. Since the VEMap.FindLocation is suggesting these addresses, shouldn't they be able to be geocoded by the same function without ambiguity?

[903 byte] By [smiller] at [2007-12-26]