Agreed here. Also a point on large repositories (most of my work I prefer to do in Mercurial but there are cases where I would prefer SVN). Mercurial at least has only a minor learning curve from SVN, while Git seems to me as if leaky abstraction is the rule. Mercurial also has far better audit control features than Git (it possesses a good superset of functionality here, including two different branching systems, one of which is designed to make it easy to audit long-lived branches).

The big problem with a DVCS is that if you are doing asset control on a lot of binary files is that when someone clones the repository they need to clone all versions of all large binary files. This is a mess. Checking out a revision and working with it is far cleaner. For example, if you are doing a lot of work on, say, PSD files, you probably don't want to use a dvcs generally as it will use needless disk space and network bandwidth for marginal benefit.

As for your 4th point, there are plenty of times I refer people to use wget to get the latest version of a file on svn from a specific branch. This is actually a very nice feature. We are looking at moving LedgerSMB to github and their subversion support makes this decision easier in part for that reason.