Yes, I think sehugg understood that, and the point was that even if you are diligent about solely using CoreData, someone else, like your ad provider, might introduce another version of SQLite in their library, so you'd be screwed anyways.
No you wouldn't. You'd only be screwed if you used that other copy of SQLite to open the SQLite file used by CoreData to store data. Which you shouldn't be doing anyway.
