Measure compiler time and memory usage when compiling code that uses eventuals

[CodingCanuck]

#454 shows that clang might be running out of memory when compiling code with many long eventuals pipelines. #275 also shows that we see slow compilation times for code that heavily uses eventuals code (maybe worse in gcc than in clang).

Let's try to actually measure the compilation cost (in time and memory) of eventuals code.

Tools that might help:

• https://stackoverflow.com/questions/15818281/profiling-template-metaprogram-compilation-time suggests several tools including a tool called templight: https://stackoverflow.com/a/28400009
• tinyformat wrote a custom compilation benchmark we could take inspiration from: https://github.com/c42f/tinyformat#compile-time-and-code-bloat (found via fmtlib: https://github.com/fmtlib/fmt#compile-time-and-code-bloat )

(I think @FolMing was interested in this topic)