CKtoph - agree. Apple can do Integration. The whole reason the don't want to do background apps is so they can have good fast swaps between applications, phone calls etc. They can do music in the background, whilst browsing, so they're perfectly capable of doing it, but they do it carefully, and basically have vetoed it unless for v. good reason that they approve of.
If the app is quitting, it can store the info so when the app is restarted, it goes right back to where it was. If you're driving along, you get a call, take it, then finish it then it'll maybe take a few seconds to recalculate position, but then, to be honest you'll be using hands free, right?
You'll probably need a few seconds to make sure you're still concentrating on the road (studies have shown that the time period shortly after a call can be distracting, not just mid-call).
The app will be hitting the A-GPS, wifi or towers as soon as it's opened if the app sees that it was mid way through a journey before a call interrupted it. (A simple poll of info held within the phone should do that).
Data dependency isn't too much of a problem - some GPS out there already pre-caches route information. Heck, if you wanted to, you could use the accelerometers to give you a fix
Don't forget also that the iPhone is likely to also have an internal compass ala Android I/O conference demo, and also have Street View - Street View shows that Google can do non-North views. If you have a compass, you just alter the data. Not too much of a technical problem to fix I imagine. If you look at Google Street View, the indicator of position shows direction also, so it could reverse that, and have the direction up, and the map rotate around it.
Why shouldn't developers code so it pre-caches the route map data? It isn't like there isn't enough storage, or data capacity through 3G / HSDPA when the signals there.