The POD normally mirrors the version number, does Perl::Version help to update this too?

And I prefer to have the usage information and licence inside separate Module.pod file.

The POD inside the the .pm will be used to generate the .pod, but will also contain information relevant for the maintainer . Like having a =head1 for Exported or Methods which will be shown in the Module.pod, while documentation for =head1 Internal subs are hidden.

Much saner, I don't need repeated informations and boilerplate when looking into code. And refactoring becomes easier.

> Test files don't need to know the module names

I'm not sure how you unit test a sub-module without use -ing it.°

update

Furthermore there is plenty of code in POD which should be tested too. Like from Synopsis, Examples and Tutorials.

°) you mean prove -M ?