-Make statstics on the half of the objects, next week delete them and make statistics on the other half
-Delete the row in dual, or make dual in the schema of the developers with no row - when they come complaining, you will use sys.dual and all will be fine (for you)
Well, here is a TRUE story that a project manager told me he did.
One of our applications release requests was so asinine/insane that his DBA at the time actually broke down in his cube over this. He actually got permission from his Systems Manager to let them do whatever they wanted and not enforce ANY business rules or RDBMS restrictions on them; he removed the DBA department from the design process entirely and let them go for it.
Needless to say they never made it past the first test phase and then humbly asked for our input into this release. Very funny and true!! I love know it all developers that think we are doing nothing but restricting them, let the lunatics run the asylum once in a while, why not?