Don't generate automatic include guards

They are useful most of the time but also a pain in the ass if you have
multiple files with the same name but in different directories (e.g. YSI).

Even worse, they didn't work with non-native directory separators in
#include directives, but that actually turned out to be useful and helped
defeat the first bug!

See issue #6.