Unfortunately it does not return the bounds of the matched feature. We use this to determine if results are accurate enough, by measuring the area of the bounds

Unfortunately it does not return the bounds of the matched feature. We use this to determine if results are accurate enough, by measuring the area of the bounds; for example, if the match is a long road (not a numbered street address), it makes no sense to use the latlng because it's quite obviously too imprecise; but if the road is quite short (less than 100m, say), it's acceptable to us. It's such an obvious feature to provide a geocoding API that I don't know why only Google does it.