Use Ruby's Set rather than Hamster::Set for optimizing #subset? and #superset? when Array is passed

This gives a *big* boost in performance.
Checked break-even points for #superset? and #subset? optimizations more carefully

It turns out the point where the optimization becomes useful is higher than I
previously thought.
Apply same optimization to Set#disjoint? as to #subset?