xbee analogin/digitalin conflict in XBee_GetIOValues

I've built an xbee-based remote control which remotely sends analog and digital data to an xbee on the make application board. I noticed one of my digital inputs was always 0 and started looking into the XBee_GetIOValues function to see what was happening. When using a mixture of digitalins and analogins a bug in XBee_GetIOValues in the heavy 1.3.1 code may cause a digitalin value to be zeroed. Basically the code goes through 15 times writing to an array of 9 values, sometimes overwriting values. For example, digitalin 6 can be loaded in one pass of the loop, and then an unused analog input can cause the digital value to be zeroed. I posted this problem and its fix into the tracker as #74.

Thanks for the report (and patch) - I'll check it out and make any appropriate changes.