Analytics counts each unique effective visitor ID as a unique visitor.
If you look at the previous table, this occurred 3 times: at hits 1, 9, and 10. This occurs because the effective visitor ID is the same for both server calls, and occurs even though the visits might be several hours apart and on different devices.
This can increase the number of unique visitors you see when cross-device visitor identification is enabled. The visitor might be counted twice on the same visit: once for the initial visit and again after the user is authenticated.
When a new visitor views your site, the s_vicookie is populated and stored. On the data collection server, a new visitor profile is created for this visitor ID, and the effective visitor ID on the profile is set to match the cookie.
When cross-device visitor identification is enabled, if a visitor ID variable is provided in a subsequent hit (for example, after authentication), the effective visitor ID is updated to match the custom value. This can cause the effective visitor ID to change directly after authentication, resulting in multiple visitor counts.
After the initial association, visit counts return to normal because the visitor is associated through the visitor ID cookie. If the visitor later views your site and then authenticates, the visitor count is not inflated because the effective visitor ID doesn't change after authentication.