Almost, but not quite, since Memchmark watches behaviour of code while the point here is to examine static data.
A helpful technique might be to duplicate data over and over in order to increase the scale (though that is not trivial, think of shared hash keys and deeply nested references) while tracking overall memory consumption, and then doing some math.