Delete by id

Going through the query optimizer causes a point delete to lock the point to be deleted plus the next index row after that (on c->advance()). This overlocking can be bad for applications that send parallel delete requests for adjacent _id values.