** Dev/Building/Publishing **
I use snapshots in my build strategies. I create a snapshot when I start a build, then use the snapshot as a “clean” source to create dacpacs, scripts, or other packagers. This allows devs or other process to continue to use the original DB for publishing, editing, coding, testing, etc without interrupting or tainting the “build snapshot” version. Timing could be an issue at any time, but it’s certainly a lot less than other strategies we’ve tried and we haven’t encountered any noticeable issues.

** Restoring a DB from a snapshot **
Also, a statement to note in the article may be that that when using Snapshots restoring a DB from a snapshot, like with the good Update strategy mentioned, realize that any other snapshots that exist for that database must be removed first. This could possibly disrupt any other strategies in use (like reporting). You’ll have to 1) drop all snapshots except the one you’re restoring, 2) revert/restore the DB from that desired snapshot, 3) recreate all other snapshots. Be conscious of this requirement.