fixed ordering of calls in setRegion to prevent segfault
fixed ordering of calls in setRegion to prevent segfault

A failed setRegion() leaves a ti_iter which shouldn't be destroyed.
Attempting to call ti_iter_destroy on it in the next call to setRegion()
will cause a segfault.  Reordering the calls avoids this issue.

ekg/tabixpp