> It seems to me that the right thing here would be to eliminate the includeOrigin option for looking up objects rather than locations, and if the user wants to delete an object, he can just remove it from the results bag.
This is I've been doing for ages. The includeOrigin parameter only
really makes sense if you have one object per location, in which case
it saves you from looping over all neighbors to remove yourself. In
the case of multiple objects per site, this can't really be avoided.
I seriously wish Java treated functions as first class objects and had
map, filter, and fold as part of the standard collections API.