ConfigMgr client computers that are powered on but are not connected to the corporate network will continue to execute hardware and software inventory processes as scheduled and will store the data locally.  Once the client is able to connect to the ConfigMgr site server and retrieve policy the client will upload the saved inventory records and the site server will assign them sequenced version numbers and typically process them in the order they were created.  This behavior can be verified in the dataldr.log on the site server.

In ConfigMgr 2012 you can have include collections to include members and you can have exclude collections to exclude members.  Makes sense, right?   But what happens if a collection member (could be a computer or a user) exists in both collections, the include and the exclude?  Which one takes priority?  The exclude would win, so the collection member would not be returned in the collection results.