Should Java Static space and Memory Model be a part of AP CS
Static is within the AP subset and is fair game for the examination.  Oddly enough, the memory model of Java that operates here is not, so students could, hypothetically, memorize a series of arbitrary rules and be fine here.

If you think it seems silly to teach about static without at least giving a passing understanding of how memory works, then you and I are on the same page.  However, in this instance, I provide a simplified (and terribly inefficient!) view of memory usage, because I don't want to delve too far down this rabbit hole in what is essentially an introductory class.  (Especially because we haven't yet covered the all-important idea of passing this as a parameter.)

Here is a picture of the PowerPoint slide with the setup itself (sans animation).  Also not seen is another slide that says, "Hey class, when can a lie serve the truth? ... Right now!")



There are more slides, and quite a bit of discussion.  But in essence, this model allows me to ask discussion questions like:


Why are there 3 Doublers in memory?
Why is there only one count?
What did static actually accomplish?
What would happen if we called val++ from inside method(). Is there any reasonable way for Java to interpret this?
What would happen if we called count++ from inside doubleVal()?  Is there any reasonable way for Java to interpret this?


Now, as for the situation you are in, it sounds like you've already devoted a lot of time to this.  I would not spend a great deal more time on static.  There is a lot in the exam, and static is not heavily tested.  I might do one more quick attempt to try to clarify this idea, but then move on.  There is, as you said, plenty else to do.