Cross street Geocoding does not work for all GeoCode type requrest?

I'm having trouble getting the address engine to accept a cross street pair to indicate a specific location.

From the 3.6.2 SDK under "GeoCoder.GeoCode Method (String, Country)" (Help file states 3.6.1 to the top):
"The geocoder is capable of looking up street intersections when they are specified with the & (ampersand) or @ characters. For example:

18th & placentia, costa mesa18th @ placentia, costa mesa"

Using maps from USA map 11Q2. Licensed client. Latest DLLs.

Our customer is experiencing failure of cross street reference. I can replicate the same problem in our development environment. Upgraded to the latest DLLs (3.6.2) without success. When using GeoCoder.GeoCode Method (String, String, String, String, Country) cross street geocoding is attempted, tried help example of "18th & placentia, costa mesa", under 3.6.2 .net DLLs, multiple entries are returned and a generic location range is part of each entry ("[500-1099] W 18th St., CostaMesa ... and [100-499] E 18th St, Costa Mesa ....). When using GeoCoder.GeoCode Method (String, Country), it does work. Does only work with that one type of call where the address is one long string? This method however can fail in other formats of geocoding. The first entry is close but 3+ streets away. I would assume that it should be a dead on match to the exact location of the cross streets.

Does this functionality actually work under all calls or only certain calls?