I suggest using a coverage struct pointer in rb_iseq_struct to hold all
3 coverage VALUEs.  rb_iseq_struct is gigantic already, so adding 2 more
VALUEs for infrequent coverage use can lead to even more bloat.