You're right, this looks like a data issue in MapPoint's base map. We notified Microsoft and it will be logged in their bug tracking system. I expect it will be fixed in the next release of the product (which unfortunately could be a year away).