title: Is it possible to get out of order didUpdateLocations when using allowDeferredLocationUpdatesUntilTraveled
body: <p>I have added <code>[CLLocation allowDeferredLocationUpdatesUntilTraveled: timeout]</code> to my app.  Most of the time everything works fine.  Every now and then I get the current location when I turn on the screen in the middle of the deferred locations.  Is it possible that the location manager would send my app a <code>locationManager:didUpdateLocations:</code> for the current location and then call it with an array of deferred locations?  About the locations passed to <code>locationManager:didUpdateLocations</code> Apple's docs say </p>
  
  <blockquote>
    <p>This array always contains at least one object representing the
    current location. If updates were deferred or if multiple locations
    arrived before they could be delivered, the array may contain
    additional entries. <strong>The objects in the array are organized in the
    order in which they occurred.</strong> Therefore, the most recent location
    update is at the end of the array.</p>
  </blockquote>
  
  <p>I didn't see anything about the order in which <code>didUpdateLocations</code> is called.  Is there any guarantee that the delegate method didUpdateLocations is called in the correct order?</p>
  
  <p>Thanks!</p>
  
  <p>Stephen</p>