for (var n in ...) not reliable

I happened to run this module in an environment where Array.prototype had two methods added ("last" and "contains" btw). And I was wondering why two undefined elements are showing up at the end of the list of items, until I realized that is why. Well. Basically if you use "for (var n in ...)" then it also enumerates the extended prototype elements, so does not work well for when you have Array extended. There is no options['last'] element in the array from the parsing of options really, so you'll end up with undefined.

To reproduce the bug, just try to pop in any of these samples to your JS and go to an options element form: http://www.go4expert.com/forums/showthread.php?t=606 You'll see a number of undefined elements equal to how many custom methods you've added.

The suggested patch just uses the boring regular for syntax to avoid running into non-numeric indexes on the arrays.