Unc path tolerant

Wouldn't it be better to fix PathUtilitities.PathsAreOnSameVolume instead of introducing a new hack here?

Seems to me that the check that is done in UnsafeForFileReplaceMethod below could be moved to PathsAreOnSameVolume - especially since you say that the same drive check fails for UNC paths.