range.js initialization in IE 8/9

Line 77 in the `$.Range` constructor is problematic if you've included jquerypp in and there's no DOM yet.

B/c `this.win.document.body` is null, `this.range` doesn't get assigned.

If this.range doesn't get assigned, the module setup (anonymous) function chokes at line 642 ( ... `fn.compare = range.compareBoundaryPoints ?` ...) and bails w/ an exception.

This is especially dangerous if you, like me, happen to have range.js concatenated w/ a bunch of other files (and minified) - those other files' initialization may not run b/c of the exception.

Start in range.js at line 77 of the $.Range constructor and trace the module setup around line 642. Reproduce loading jquerypp in the document head before a body exists, then verify that range.js no longer throws and that initialization of subsequent concatenated modules still runs.

Written by the indexing model from the issue text.