Differentiate ops that access class attributes from the rest

[llorllale]

Following on from this comment:

We need a way to differentiate <op> that access the class' attributes from other ops that don't. LCOM5 (#18) needs this.

[0crat]

@yegor256/z please, pay attention to this issue

[yegor256]

@llorllale but we have it already. If an op accesses an object attribute it has type equal to put or get.

[llorllale]

@yegor256 sorry, did not see it documented anywhere (and didn't look at code). Are the plans to add more types that access attributes? Will fixing #114 involve adding a new type?

[yegor256]

@llorllale maybe, if new metrics will require them.

[0crat]

Job gh:yegor256/jpeek#123 is not assigned, can't get start time

[0crat]

Job #123 was not in scope