When a real-time Bounce to Disk ends prematurely because of any error (90% of the cases are CPU spikes that stop it in random points), don't delete it, letting the user running another bounce from the point it stopped!
Realtime bounces are still needed when passing through analog hardware. I'm using Pro Tools since 2004, and since then I had the problem of bounces stopping randomly; so I find myself running smaller, separate bounces and merging them. I know that this is silly - but sometimes is the only workaround possible.
The Bounce to disk command could even restart and merge the separate bounces automatically.