OSAL has a concept of tables of resources, where the user can configure some maximum amount of those resources.

For example, the binary semaphore table could contain the static bytes of memory for the semaphore itself (using VX_BINARY_SEMAPHORE or an array of size VX_SEMAPHORE_SIZE taking care to maintain proper alignment) and then use semBInitialize on that memory when the OSAL wants to create a binary semaphore instead of allocating one from the resource pool. The user configures the maximum number of resources of each type, so it's ok to use the memory.

This enhancement would increase determinism in the system while maintaining the current API.