The only thing wrong with statmobile's way of doing it (other than its break from the *nix philosophy of laziness) is that the files are copied from one location on the hard drive to another, taking up double the amount of space and causing the operation to take longer. In contrast, the move does not actually change the physical location of the file, it simply changes the place that the files can be found inside your operating system. (I'm sure there are exceptions to this, such as in the case of mounted devices and whatnot)
At least that's my understanding of what cp does. I might be wrong and that it creates a hard link where it's being copied, rather than creating a whole new copy, although that would be inconsistent with the typical behavior of copy.