checkasm: Validate the benchmark call configurations even if not benchmarking

This should help catch issues like the one fixed in 185194be, by making sure that we call the benchmarked function at least once with the given parameters, even if not benchmarking. Otherwise the benchmark codepath is essentially dead untested code until somebody works on that piece of code.