Feature/disjoint

1. Add implementation for `disjoint` for the combinations:
   * point/multipoint
   * multipoint/multipoint
   * multipoint/segment
   * multipoint/box

2. Add test cases for the combinations above

3. Update support status table for `disjoint`
Sorry I wasn't clear enough. Regarding the name I had multipoint_geometry in mind. This is an algorithm for Segments/Boxes, not arbitrary Geometries.

Regarding the check_iterator_range, of course in the case of find_if, UnaryPredicate/function object should be passed. I also understand that the currently used approach is in-line with the rest of the BG code. I just wanted to indicate that instead of this template there could be a single line (using Boost.Range algorithm):

return boost::find_if(multipoint, intersects_pred) == boost::end(multipoint)