`check-expect` snip output unfriendly

The following error-scenario seems unnecessarily unfriendly, and I'm wondering if something nicer is possible.

A student might write the following test program:

#lang htdp/bsl
(require 2htdp/image)
(check-expect (circle 10 'outline 'black) 'o)

This test will fail. The student receives an error message containing a snip that contains the expected value. Our student then---mistakenly, accidentally, or what have you---then picks up the whole snip and drops that in as a replacement expect value.

Now that student sees the even more confusing:

Actual value . differs from (instantiate (class ...) ...), the expected value.

This seems especially injurious because it shows up when a student is already grappling with code that isn't behaving the way he expects. I for one do not know how to explain this behavior in a way that makes good sense to a BSL student. Is something nicer is possible?

I do not know if this properly belongs here, or in the htdp repo, or elsewhere.

Reproduce the check-expect failure in DrRacket with the htdp/bsl and 2htdp/image example from the issue. Trace how the expected-value snip is presented and then interpreted when pasted back into a test; done means the resulting error remains understandable to a BSL student.