Yeah, I'm using ```Incident_Model::delete()``` 'cause it cleans all the related tables as well. 
Defs not efficient. Didn't consider the scale here, sorry!
Could run a straight TRUNCATE on all relevant tables, but I'm not sure how that will affect other things.

Just ran a test on the Zombie reports with 751 entries. It didn't struggle too much having in mind I have an old computer (took around than 10 seconds to come back). What's the worse case we can get? Considering that this is a function that won't be used too much, and the use case shouldn't apply during high traffic times I'm not sure how big an issue this is.

Having said that, I'm happy to batch them too, as it is a more elegant solution. How we do batch stuff currently? (Couldn't find anything trying to find something like that on the code...)