I'd say if you measure programming work by how long it takes until there are no more serious bugs vs the number of features, then it's highly likely that any well scoring code will also have relatively low LOC count for the number of features, as soon as there is anything non-trivial required from the code.
Besides, large LOC count isn't bad in itself. It's just that if there's duplication in the code, then if said duplication has to be changed (say, there's a bug, or requirements change or expand) then the changes have to be made in several places, and this is where the problems come.
Hence, for any non-trivial combination of features, only well written code is ever likely to reach the point of "no more serious bugs." Ofcourse the code might not starts it's life as "well written" but sooner or later it has to be refractored, if continued maintenance with finite time investment is desired.