It seems that running RFduinoBLE.begin() causes the micros() and millis() functions to jump to very high numbers. I'm consistently getting 3557034959 microseconds and a similarly high millisecond value. This goes away when I remove bluetooth initialization and occurs regardless of where I put the function into my code. I can easily set my variables to start at 3557034959 rather than zero to track time, but this seems like something that shouldn't be happening outside of my code.
Hoping somebody can duplicate this elsewhere.