The Einstein quote is that "something should be a simple as needed but no simpler", but how to be pin down "required" in an objective / quantifiable way?

Somehow it is more important to measure "gratuitous" complexity, redundant complexity that is not justified by present or plausible future requirements...

The problem is that the code itself does not capture requirements, so code analysis can give you absolute indicators but never an "efficiency" measure (how efficient and justified the measured complexity)