That case sounds like a bug/algorithm issue with address lookup software. If the OSM data is correct, then it would make the same mistake with any other correct map data source, right?
But in this case, it sounds like the issue is that a private driveway is mis-labelled as a public route. This sort of thing is trivial to fix in OSM.